Recently , I had to configure a SIP trunk to operate with Microsoft Exchange as voicemail system but as the integrator of the exchange doesn’t know a lot about his system , he was unable to configure the voicemail boxes with the correct number so it gave me some mistake as Exhange was unable to resolve the called number . So after some searches , I found that we can use the SIP Normalization as in the CUBE but this time directly in the CUCM .
The SIP normalization for SIP trunk on CUCM is based on lua ( an old application language) but even if you have no complex structure , you can easily modify the SIP stack in the inbound and outbound direction.
So you need to read the cisco documentation to master but after an half day you can already play with it to have something.
Lua is really something that you need to try when you need to update a little your sip fields/option and which is really powerful . I will come on later on this post to put a short example.
It can seem dumb , but I’ve just played/discovered the ATA 187 ( which is working in SIP) . while I was trying to enter in the IVR menu , I was prompted for a password that we have not in the past.So after one or two google line , I finally discovered that the default password is cisco ( yeah I know , they are very hard 🙂 ) , so in numeric it is giving you 24726.
numb advise of the day 🙂 lol
I came across your blog when doing some research and its totally great. I have been struggling with getting CUVA to work with our deskphones.
To give you a quick background, we are running UCCE version 7.5. Our Desk phones are 7941’s with the latest firmware (9-1-1SR1S). All deskphones are configured as SIP.
Im running Video Advantage verion 2.2 (which supports SIP video) and cannot get the phone to integrate with the video software. CUVA works perfectly fine with a deskphone. One theory I had was the windows firewall was blocking CUVA from speaking with the 7941 but after disabling it, Im still experiencing the issue.
Is there soemthing major that Im missing, which is causing the webcam to no communicate with the phone?
Just as a reminder when you sit in the lab, try to not forget to put the correct Calling number , type and plan and this for all situation so it is true as well for SRST.
So a good vision of the call routing is important
Sometimes , when you defined your mgcp config and before to activate it with the CUCM config. You can experience issue where you can not send or receive calls on this gateway only because your link is not up.
This is caused because the binding between the MGCP gateway and the CUCM is not properly set up. So in order to fix this issue under your serial interface , remove the command isdn bind-l3 ccm-manager and put it again just after. The result is direct and your PSTN will go up .
Here is a basic stuff to implement the mgcp config
ccm-manager redundant-host 172.17.123.201
ccm-manager config server 172.17.123.200
mgcp call-agent 172.17.123.200 service-type mgcp version 0.1
mgcp bind control source-interface GigabitEthernet0/0.102
mgcp bind media source-interface GigabitEthernet0/0.102
mgcp profile default